Skip to content

Load standard role profiles from the store, not source - #7

Merged
daniel-rossier merged 1 commit into
mainfrom
standard-profiles-from-store
Nov 13, 2026
Merged

daniel-rossier merged 1 commit into
mainfrom
standard-profiles-from-store

Conversation

@daniel-rossier

Copy link
Copy Markdown
Contributor

The harness no longer hardcodes any particular standard. Complements #6 (which genericised docs and comments); together they take the worked example out of the public source entirely while the standard itself stays private, shipped in the store and baked only into private images.

What changed

  • Role profiles are data. RoleTaxonomy.from_mapping deserialises a profile.json a standard ships beside its ingested revision in the store; standard_profiles.register_for loads it at bind time (StandardOperator._register_profile), best-effort. A standard with no profile keeps the conventional reading.
  • The hardcoded taxonomy is gone. The old ANSI-VITA-49.2 role taxonomy was byte-for-byte identical to CONVENTIONAL, so removing it changes no behaviour — it just stops naming a standard in public source.
  • Standards bodies are configurable. normative_claims keeps only the common bodies and takes the rest from SPEAR_STANDARD_BODIES, so a deployment adds its own without touching source.
  • Tests bind a neutral EXAMPLE-STD-1.0 example throughout (26 files).

Validation

Full suite run with the configured venv: 4470 tests, all green except one pre-existing, unrelated failure (test_environment_namespace, about SPEAR_REDS_* shell variables already on main).

…urce

The harness no longer hardcodes any particular standard. The role taxonomy a
standard needs when its labels mean something other than the conventional
reading now travels with its data: a profile.json beside the ingested revision
in the store, loaded at bind time (StandardOperator._register_profile), so it
reaches an image with the document and is never named in this public source.

- normative_force.RoleTaxonomy.from_mapping deserializes a stored profile.
- standard_profiles.register_for loads it best-effort; a standard with no
  profile keeps the conventional taxonomy. The hardcoded ANSI-VITA-49.2
  taxonomy, which was byte-for-byte the conventional reading, is gone -- no
  behaviour change.
- normative_claims names only the common standards bodies and takes the rest
  from SPEAR_STANDARD_BODIES, so a deployment adds its own without touching
  this source.
- The test suite binds a neutral EXAMPLE-STD-1.0 example throughout.

Full suite green apart from one pre-existing, unrelated failure
(test_environment_namespace, about SPEAR_REDS_* shell variables on main).
@daniel-rossier
daniel-rossier merged commit 091d2a4 into main Nov 13, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant